Tech Notes for CDR Publisher Last Modified date: July 5, 1996 **** Down Load The Latest Versions with Bug Fixes and Enhancements **** **** From http://www.cdr1.com **** PC Windows: Version 4.6 PC Windows NT: Version 4.6 PC Windows 95: Version 4.6 SunOS: Version 4.6 Solaris: Version 4.6 SGI: Version 4.6 Most of the background information is placed in the latest version of the manual. We highly recommend that you take a look at the following sections before you start: Page 45 Create Image by Different Methods Page 68 Create Image to a CD-ROM Recorder Page 83 Using Virtual Disk * Updated Sections 1.0. General: 1.1. Difference between the Demo, Lite, and Full featured versions. 1.2. Run CDR Publisher on different platforms. 1.3. Run CDR Publisher on different machines on the same platform. 1.4. What is the expected turn around time for a license. 1.5. I have send my e-mail license request but did not get a reply. 1.6. Check list for debugging installation problems for PC versions. * 1.7. Check list for debugging installation problems for UNIX versions. 1.8. Various features of the Recorders and CDR Publisher. * 1.9. Running CDR Publisher on Windows 95. 1.10. Preserving long file names in Windows 95 and Windows NT. 1.11. Driver conflict with other CD Recording Software. 1.12. Note for UNIX user's with Philips 2000, HP 4020i, and Plasmon recorders. 1.13. Create New Directory inside HyCD. * 1.14. Created unmountable CDs. * 1.15. Using Advansys's SCSI controler. 2.0. Developer's Kit: Command Line interface to CDR Publisher: 2.1. Integrating CDR Engine into your application. 3.0. Virtual Disks, Image Files: 3.1. Create multiple CD images and store them on a hard disk. 3.2. Mounting the Virtual Disk Back as a CD-ROM. 4.0. Hybrid CDs: 4.1. Mounting hard disk as a PC Exchange Disk onto the Mac system. 4.2. Retaining NT long file names. 4.3. Retaining Mac long file names. 4.4 Selecting Files to be included into HyCD. 5.0. Music CDs: 5.1. Control the gaps between audio tracks. 6.0 SGI EFS CDs: 6.1 Building SGI EFS CDs. 7.0 Bootable CDs: 7.1 Obtaining a floppy bootable image or IDE hard disk bootable image. ---------------------------------------------------------------------------- 1.0. General: 1.1. Difference between the Demo, Lite, and Full featured versions. CDR Publisher can be run in demo mode or in licensed mode. Demo Mode: You can run CDR Publisher in demo mode by selecting the "Demo" button when the software is first started. Try out all the features in CDR Publisher including creating Hybrid CD-ROM for PC, Mac, and UNIX. The only limitation you have is that you can only create CD-ROM images less than 5 MB in size. Licensed Mode: You can run CDR Publisher in licensed mode by selecting the "Register" button when the software is first started. A Window will pop up for you to fill in your name, address, telephone number, and software registration code. The registration code is located on the inside cover of the CD case. You can also obtain a promotional Registration Code for the Lite Version from our web site until June 96. Press the "License Request" button and generate a License Request File. E-mail the License Request file to "license@cdr1.com" or fax the printout to (408) 255-1011. After requesting a license and obtaining a password, CDR Publisher will be activated in the following modes: Lite, HyCD, or HyCD Multimedia. A UNIX Lite version can only create ISO with RRIP data CDs. A PC Lite version can only create ISO data CDs. A Lite version can not create any foreign type of CDs. A HyCD version can create Hybrid Data CDs, including HyCD, EFS,and UFS CDs. A HyCD Multimedia Version can create HyCD, Audio, Mixed Mode, CD Plus, CD-I and Video CDs. You can find out what version you have by selecting "Help/About..." in the Main Menu. 1.2. Run CDR Publisher on different platforms. Each license an end-user obtains is for a specific platform, i.e. Windows, Windows NT, Windows 95, SunOS, Solaris, SGI. The platform is determined when you install the software and register under a specified platform. To run CDR Publisher on a new platform, i.e. upgrading from the Windows 3.1 to Windows 95 version, please contact CDR to obtain an Upgrade. To run CDR Publisher on additional platforms, i.e. running both on Windows 3.1 and Windows 95 or running on multiple machines, please contact CDR to purchase additional licenses. 1.3. Run CDR Publisher on different machines on the same platform. If you only have one license (you purchased a single copy), you should install the software on one computer and use it. If you have reinstalled the OS, or need to reinstall the software or move the license onto another system: A. Destroy the old copy on the old system. B. Install the software onto the new system. C. Use the same Registration Code to run the Register Program again. D. E-mail the License Request Form to CDR. E. Creative Digital Research will update its database and issue a new password to you. F. When you have obtained a new Password from CDR, type in the new Password and activate CDR Publisher on the new system. 1.4. Expected turn around time for a license. E-mail: within 1 minute after e-mail reaches CDR. Fax: 24 hours during normal business hours. 1.5. I have sent my e-mail license request but did not get a reply. Please check your "From" field on the e-mail that you've sent. It is possible that the mail is undeliverable because of the wrong return address. 1.6. Check list for debugging installation problems for PC versions. A. Always download the latest version/patch of CDR Publisher from our web site: http://www.cdr1.com B. Using Adaptec SCSI Controller Card or 100% compatible SCSI Controller Card. C. Enabled SCSI "Connect and Disconnect" and "Sync" features on the SCSI Controller Card. D. Installed 100% compatible WinASPI driver from EZSCSI 4.0, or above (Downloadable from web site: http://www.adaptec.com ) E. In the Main Window, Configure/Hardware/Source and Destination windows are configured to match your hardware devices. F. In Main Window, Configure/Hardware/Destination/CD Recorder/Optimize Window: Press the "Default" button to set everything to default. G. Make sure you have more available disk space than your Virtual Memory setting. To reset Virtual Memory: Please run Control Panel/386 Enhanced/Virtual Memory, set it to None. Exit Windows. Run Scandisk and defrag. Restart Windows, run Control Panel/386 Enhanced/Virtual Memory, and set Permanent > 20 MB on a hard disk with at least that amount of space. H. To test communication between the CD-ROM Recorder and the System, turn on "Virtual Write" in the Recorder setting window. 1.7. Check list for debugging installation problems for UNIX versions. A. Always download the latest version/patch of CDR Publisher from our web site: http://www.cdr1.com B. Make sure the driver is loaded by running the installation script for install. To reload the driver, run "cdrdrv.load" command. C. We recommend that you use a Virtual Disk if you are running CDR Publisher in a multi-user, multi-process environment to prevent Data under-run. D. If you are using Virtual disk, make sure the recording device file is Writable. SunOS: Virtual Disk is SCSI ID 2, Partition b % chmod 777 /dev/sd2b Solaris: Virtual Disk is SCSI ID 2, Partition 1 % ls -l /dev/rdsk/c0t2d0s1 You will get: lrwxrwxrwx 1 root root 55 Feb 22 18:48 c0t2d0s1 -> ../../devices/sbus@1,f8000000/esp@0,800000/sd@2,0:b,raw* Chmod on the raw device: % chmod 777 "../../devices/sbus@1,f8000000/esp@0,800000/sd@2,0:b,raw" SGI: Method #1: Use an entire hard disk as Virtual Disk Benefit: May be able to mount back and test the Image. % chmod 777 /dev/scsi/* Select the Virtual Disk as your destination in the Main Window. Method #2: Use a partition of a hard disk as Virtual Disk Drawback : Not able to mount back and test the Image. % chmod 777 /dev/rdsk/dks0d20s1 Select the Image File as your destination in the Main Window. Set the raw device file as your file name. E. Make sure your Virtual Disk or Image File resides on the local system. If your source files reside on another system, you should definitely use a local hard disk drive as a Virtual Disk or Image File to store your CD-ROM Image before you output it to the CD Recorder. F. Source "cdrenv" before you start. For convenience, place the content of cdrenv into your .cshrc file. G. Always run CDR Publisher in a writable directory, i.e. /tmp. If you do not, you will see "Error" and empty Log Window. H. To test communication between the CD-ROM Recorder and the System, turn on "Virtual Write" in the Recorder setting window. I. For Sun running Solaris operating system, do not use /tmp as a place to store Image Files. /tmp is generally too slow because it is on a swap partition. J. Make sure you are in a writable directory when you start cdrpub. If not, you will see empty Error Log Window. 1.8. Various Features of the Recorders and CDR Publisher You can find out various features of the CD-ROM recorders and what CDR Publisher supports by selecting the Help/CD Device Features menu item in the Main Window. 1.9. Run CDR Publisher on Windows 95. Currently all the Windows 3.1, Windows for Workgroups, Windows NT and Windows 95 versions are designed and optimized for the individual platforms. Please run the individual binaries on specified platform. Update to Windows 95 version by downloading from: http://www.cdr1.com/download.htm Update your Adaptec EZSCSI 4.0 driver by downloading the driver from: ftp://ftp.adaptec.com/pub/BBS/dos/ez40up.exe And Update your WinASPI drivers from: ftp://ftp.adaptec.com/pub/BBS/winnt/aspi32.exe ** Do not update the WIN95MPD.EXE driver because it has not been tested. 1.10. Preserving long file names in Windows 95 and Windows NT. Windows95 and NT do support longer filenames, but their CD-ROM driver does not. To create a CD that is able to be read in both environments, you must select PC format with ISO Level 1, File/Dir Name not enforced, include ";1", or the CD would not work properly. If you'd create a CD with ISO Level 2, you will see long file names but you will not be able to access the files in the NT environment. With CD created by process described above, you will see NT "display" all files in upper case, but you can access all the files. You will see Windows 95 display with both upper and lower case and you can also access all the files. This is using a "bug" in the OS to get around the OS limitation. Windows95 supports Joliet file system for long file names. But not Windows NT. Within one month, we will have Windows 95 version that will create: HyCD = PC (ISO 9660) + Mac (HFS) + UNIX (RRIP) + Win95 (Joliet) hybrids all together on a single CD. This way, we can provide you with proper support for all environments. 1.11. Driver conflict with other CD Recording Software. If you are using device drivers from other CD-ROM Recording software; i.e. Incat Systems' EASYCDMS driver, comment it out. For example change: DEVICE=C:\ECDMM\EASYCDMS.SYS /D:CDWO to REM DEVICE=C:\ECDMM\EASYCDMS.SYS /D:CDWO 1.12. Note for UNIX user's with Philips 2000, HP 4020i, and Plasmon recorders. If you are using the following CD-ROM recorders: Philips 2000 HP 4020i Plasmon 4220 Please turn off the power to the CD-ROM recorder before you boot up your system. Once your system is in multi-user state, turn the power to the recorder back on, then proceed. 1.13. Create New Directory inside HyCD. Currently, our GUI allow you to select original directories to be included into HyCD. It does not allow you to create new directories inside the HyCD. We will add this feature into our future release of CDR Publisher. 1.14. Created unmountable CDs. If you have created a CD that is unable to mount in any systems. Please check if you had performed a Virtual Write operation. Turn off Virtual Write function in Hardware Configuration Window and perform a Physical Write. If you are have performed a physical write function, please try to mount the CD back from a different system with different reader. It is possible that there exist an incompatability between the CD-R media, the Recorder, and the CD Reader. Please call your CD-ROM Recorder company for a list of recommended CD-R media. 1.15. Using Advansys's SCSI controler. Advansys SCSI controller is what HP bundled with their CD-ROM Recorder. Currently, there is an incompatability between our software and the Advansys SCSI driver. We are in the process of porting our software to support the Advansys's SCSI controller cards. 2.0. Developer's Kit: Command Line interface to CDR Publisher: 2.1. Integrating CDR's HyCD Engine into your application. You can use the Command Line interface to CDR's HyCD Engine and integrate its CD recording capabilities into your existing application. The Developers Kit contains information on how to do it. Download the Developer's Kit for FREE from our web site at: http:/www.cdr1.com 3.0. Virtual Disks, Image Files: 3.1. Create multiple CD images and store them on a hard disk. You can create multiple Image Files residing on a formatted file system. If you are using a UNIX system, you can create multiple images and output to the raw partitions of the device files. i.e. /dev/rdsk/.... 3.2. Mounting the Virtual Disk Back as a CD-ROM. You can follow the instructions described on Page 83 of the manual. We have found that some hard disks are not capable of being used as a Virtual Disk on the SGI Platform. This is due to the limitation that the hard disk unable to "fool" the CD-ROM Reader driver into treating a hard disk as a CD reader. Creative Digital Research has reported this limitation to Silicon Graphics and trying to find a work around. 3.3. Use a partition of the hard disk drive as a virtual disk? With UNIX systems, a Virtual Disk can be a partition of a hard disk. You can select the source/destination to be an Image File and read/write the CD-ROM image to a raw device file name: SunOS: /dev/rsdxx Solaris: /dev/rdsk/cxtxdxsx SGI: /dev/rdsk/dksxdxsx With PC systems, Virtual Disk must be a entire hard disk. It cannot be a partition of a hard disk. If you currently have a large drive, you can use Image File instead. To increase the disk accessing performance, defrag the Hard Disk. 4.0. Hybrid CDs: 4.1. Mounting Hard Disk as a PC Exchange Disk onto the Mac system. You can first format the hard disk drive from the PC. Take it to a Macintosh system and mount it back as a PC Exchange Disk; see page 74 of Manual. We have found that some hard disks are not capable of being used as a PC Exchange disk. This is due to the limitation of the Macintosh PC Exchange driver. Some users of CDR Publisher have successfully used SCSI based ZIP or SYQUEST drives to move data across. You may wish to try to do so. 4.2. Retaining NT long file names. Windows NT 3.51 currently does not support ISO Level 2. If you have created one, you may see the directory, but you can not "cd" into it. Windows NT supports ISO Level 1. Without dir/file name enforced, you can create a CD that will preserve the long file names. All the file names will display as upper case but you can access them by typing the lower case letters. In the future, Windows NT will support the Joliet file system which supports long file names. Our next version of CDR Publisher will support the Joliet File System at the end of May. When these two systems match, you then will get proper support. 4.3. Retaining Mac long file names. Please note that DOS path names are restricted to 64 bytes. For example: C:\path1\path2\...\pathN\file_name.ext ^ ^ |-- Max Length <= 64 --| If your Macintosh files has long path names, please reduce it before you copy it to a PC Exchange Disk. 4.4. Selecting Files to be included into HyCD. When you select the files to be included into HyCD, you can use 'Add All' to add all the files and directories in the PC Exchange Disk into HyCD. If you only wish to add some individual files, you must select both the file(fn.ext) and its resource fork (fn.frk) to be included into HyCD. 5.0. Music CDs: 5.1. Control the gaps between audio tracks. Current with all the recorders we support, we use Track At Once to record the audio tracks. The 2 second gap is automatically recorded by the CD recorder. With the Sony recorder, we use Disc At Once technique when we record the data track. As we are enhancing the program, we will begin to support Disc At Once Recording. This will enable you to control the PQ channel and have better control of the post gap. Please look at Help/CD Device Features for a description of these features. 6.0 SGI EFS CDs: 6.1 Building SGI EFS CDs. Follow the instructions written in the manual P.101. Make sure you also "Preserve 0-15 block". 7.0 Bootable CDs: 7.1 Obtaining a floppy bootable image or IDE hard disk bootable image. In the manual we describe that you can extract a SCSI bootable image by using Source=Virtual Disk, Destination=Image File, Create Image. The following describes how you can extract a bootable image from a floppy disk. The same procedure can be used to extract bootable IDE hard disk drive. 1. Run Norton Disk Edit program. The editor will come up and read your primary hard drive. 2. Open Object menu and select a: then select physical. 3. Select all sectors of the A: drive: Open edit menu and select mark. then press 'end' key to select all of drive A: 4: Open the tools menu and select write to file. 5. Name the file with the extension of '.img' Use this file as your boot file of floppy disk image.